-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add NSG monitoring for preconfiguredNSG #3156
Conversation
Please rebase pull request. |
aceb852
to
2a6a52b
Compare
Please rebase pull request. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, thanks for addressing the comments!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR is a good work. I like the fact that it opens the door to make the other monitors run concurently.
I am tentative approving this one. Good work and I do not see anything that would break exiting code.
c.Monitor(ctx) | ||
monitors = append(monitors, c) | ||
allJobsDone := make(chan bool) | ||
go execute(ctx, allJobsDone, &wg, monitors) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So we essentially introduce concurent mechanism to run multiple monitors.
We might as well migrate the rest to use this pattern, because sequential run we have in the original code is error prone.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR is a good work. I like the fact that it opens the door to make the other monitors run concurently.
I am tentative approving this one. Good work and I do not see anything that would break exiting code.
Which issue this PR addresses:
Fixes: ARO-3391
What this PR does / why we need it:
Adding monitoring for NSG and emitting metrics when invalid NSG configurations have been detected, including when the FP (the one performing the monitoring) loses access to the NSG.
Test plan for issue:
How did you test that this PR works?
Is there any documentation that needs to be updated for this PR?
N/A